Utilities

In the Utility module, you can now import utility readings with zero values for Meter Reading, Demand Reading, Consumption, and Demand Consumption, capturing accurate data.

Schedule

When you input Estimated Labor Hours in a schedule and generate work orders, any updates via the workorders API now preserve the exact labor hour values, maintaining consistency on the Work Order Request Details page.

Work Order

You can now assign or reassign work orders without encountering MVC (Model View Controller) errors.

Work Order

When adding watchers to a work order, your selections persist and all existing watchers remain visible, even with special characters in their names.

Create Request

Adding watchers on the Create Request page now retains your selections even after choosing a Crew, ensuring they stay selected through page reloads and updates.

API

The PATCH method for incidents is enhanced with validations and security checks. You need Access Incidents, Find Incidents, and Update Incidents rights, along with View Confidential if needed, to make changes.

The method checks required fields like Property, Space/Floor, Incident Type, Sub Type, Status, Department, Location, Incident Date, Root Cause, and End Date against system configurations.

Incident Date and End Date can't be set in the future, Asset IDs must be valid, and Recovery Costs are displayed when relevant. All necessary fields must be complete for a successful response, and only users with the correct security settings can perform a PATCH request.

API

When you issue items to work orders, the Work Order Financial page now reflects the issue date in your property's local time zone, aligning the UI with the ItemTransactions API to ensure consistency.

API

Named and Unnamed Guest users are restricted from using the GET or PATCH methods for incidents in the API. The User-Defined Fields (UDFs) expand now includes FieldId, Id, and Value. To use the GET method, you need Access Incident and Find Incident rights, and View Confidential for confidential incidents. Access to the incident's Region/Property is also required.

System Admin status does not override these access requirements. Additionally, you can expand UDFs when using the GET method for incidents.

API

You can now create or update User-Defined Fields (UDFs) for an incident using the endpoint: /incidents(ID)/udf. Make sure your input includes FieldId as an integer and Value as a string.

For successful operation, your permissions should match those required for POST and PATCH on incidents, and data validations will check that the FieldId exists, is part of the 360Incident UDF Application, and matches the Incident Class of the provided Incident ID.